Release 10.1A: OpenEdge Development:
Java Open Clients

INPUT parameters

Table 4–1 shows the 4GL-to-Java data type mapping for INPUT parameters.

Table 4–1: Progress 4GL-to-Java data type mapping for
INPUT parameters                                                                    

Progress data type	Java proxy data type
CHARACTER	java.lang.String
COM-HANDLE	com.progress.open4gl.COMHandle
DATASET DATASET-HANDLE1	com.progress.open4gl.ProDataGraph
DATE DATETIME DATETIME-TZ	java.util.GregorianCalendar
DECIMAL	java.math.BigDecimal
HANDLE	com.progress.open4gl.Handle
INTEGER	int
LOGICAL	boolean
LONGCHAR	java.lang.String
MEMPTR	com.progress.open4gl.Memptr
RAW	byte[ ]
RECID	long
ROWID	com.progress.open4gl.Rowid
TABLE TABLE-HANDLE	com.progress.open4gl.ProDataGraph When mapped as a Java SDO DataGraph.1
TABLE TABLE-HANDLE	java.sql.ResultSet When mapped as an SQL ResultSet.1
WIDGET-HANDLE	com.progress.open4gl.Handle

1ProDataSet (DATASET and DATASET-HANDLE) and temp-table (TABLE and TABLE-HANDLE) parameters require special handling, including the mapping of temp-table fields. For more information on ProDataSet and temp-table parameters, see the "Passing temp-tables and ProDataSets" section.

The COM-HANDLE, HANDLE, RECID, ROWID, and WIDGET-HANDLE 4GL data types are not meaningful outside the Progress environment. Their use is restricted to obtaining the value from a Progress procedure and passing it back to another Progress procedure.

Note: The Progress 4GL BUFFER parameter type is not supported in Java Open Clients.